home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Format CD 49
/
Amiga Format CD49 (2000-01-17)(Future Publishing)(GB)(Track 1 of 3)[!][issue 2000-02].iso
/
-serious-
/
misc
/
mmulib
/
fixes
/
fixes.readme
< prev
next >
Wrap
Text File
|
1999-11-29
|
5KB
|
147 lines
This directory contains various fixes for CBM programs and third-party
products, either recommended of the MuTools or for general system house-
keeping.
_____________________________________________________________________________
spatch
This is a tool program to apply patches to system components. Details about
its use are presented below.
_____________________________________________________________________________
mathieeedoubbas.pch
This is a fix for the mathieeedoubbas.library V38. The patch fixes the
MathIEEE comparision that is broken in the library, negative numbers are
sometimes ordered in the wrong way.
How to apply the patch:
Open a shell, then change the current directory to this directory by
CD <MMULib>/Fixes
where <MMULib> is the directory where you unpacked the archive to. Then make
a copy of the original version of the mathieeedoubbas.library, and keep it
in a safe place. For example:
copy LIBS:mathieeedoubbas.library to SYS:Updates
Then enter the command
spatch -oram:mathieeedoubbas.library -pmathieeedoubbas.pch libs:mathieeedoubbas.library
This will build an updated version of the mathieeedoubbas.library in ram:
Just copy it back to LIBS: by
copy ram:mathieeedoubbas.library to LIBS:
_____________________________________________________________________________
SetPatch.pch
An experimental patch for SetPatch 43.6. If applied, SetPatch will try to
open the 680x0.library instead of the 68040.library, regardless of the
processor found. It's then the matter of the 680x0.library to detect the
processor in use, and to load the appropriate processor driver library, might
it be the 68040.library, the 68060.library or the 68030.library. To run the
patched version of SetPatch, you *MUST* install the 680x0.library in LIBS:
How to apply the patch:
Open a shell, then change the current directory to this directory by
CD <MMULib>/Fixes
where <MMULib> is the directory where you unpacked the archive to. Then make
a copy of the original version of SetPatch, and keep it in a safe place.
For example:
copy C:SetPatch to SYS:Updates
To apply the patch, enter
spatch -oram:SetPatch -pSetPatch.pch C:SetPatch
The updated edition of SetPatch will appear in RAM: Just copy it back to C:.
copy ram:SetPatch to C:
Don't forget to install the 680x0.library by:
copy <MMULib>/680x0.library to LIBS:
_____________________________________________________________________________
narrator.device.pch
The narrator device stack is setup a bit too small, which might cause
warnings if MuGuardianAngel is used. This patch increases the stack size
of MuGuardianAngel.
How to apply the patch:
Open a shell, then change the current directory to this directory by
CD <MMULib>/Fixes
where <MMULib> is the directory where you unpacked the archive to. Then make
a copy of the original version of the narrator.device, and keep it in a safe
place. For example:
copy DEVS:narrator.device to SYS:Updates
To apply the patch, enter
spatch -oram:narrator.device -pnarrator.device.pch DEVS:narrator.device
The updated edition of SetPatch will appear in RAM: Just copy it back to C:.
copy ram:narrator.device to DEVS:
_____________________________________________________________________________
FixCybAccess
This fixes a flaw of the cybscsi.device, which accesses a non-allocated
chip-RAM location periodically on SCSI I/O. This program should be "run"
in front of MuGuardianAngel to prevent warnings about this bogus access,
i.e. a
run <>NIL: FixCybAccess
will do it.
More details are in the FixCybAccess.readme.
_____________________________________________________________________________
PatchRAM
A fix for two features of the RAM disk. First of all, it is also too low
on stack and will generate warnings if MuGuardianAngel is active, for
good reason. Second, the RAM disk shows always up as "100% full", which I
regard as pretty annoying. To install this fix, run it *BEFORE* accessing
the RAM disk for the first time. A good place for this program would be
directly after SetPatch.
More details are in the PatchRAM.readme.
_____________________________________________________________________________
ConsoleFix
This repairs a a bug in the console.device supervisor task which appears on
window resizing. Due to a programming fault, the device doesn't go thru all
its windows correctly if one of its client windows is resized. Luckely, this
doesn't seem to be fatal as long as the console.device gets enough stack
space.
Details about how this fix works are in the ConsoleFix.readme
_____________________________________________________________________________